The BIG-IP ASM module must be configured to update malicious code protection mechanisms and signature definitions when providing content filtering to virtual servers for whenever new releases are available in accordance with organizational configuration management policy and procedures.

Overview

Finding ID	Version	Rule ID	IA Controls	Severity
V-214506	F5BI-AS-000109	SV-214506r396024_rule		Medium

Description
Malicious code protection mechanisms include, but are not limited to, anti-virus and malware detection software. In order to minimize any potential negative impact to the organization caused by malicious code, malicious code must be identified and eradicated. Malicious code includes viruses, worms, Trojan horses, and Spyware. This requirement is limited to ALGs, web content filters, and packet inspection firewalls that perform malicious code detection as part of their functionality.

Description

Malicious code protection mechanisms include, but are not limited to, anti-virus and malware detection software. In order to minimize any potential negative impact to the organization caused by malicious code, malicious code must be identified and eradicated. Malicious code includes viruses, worms, Trojan horses, and Spyware. This requirement is limited to ALGs, web content filters, and packet inspection firewalls that perform malicious code detection as part of their functionality.

STIG	Date
F5 BIG-IP Application Security Manager Security Technical Implementation Guide	2024-01-25

Details

Check Text ( C-15713r290532_chk )
If the BIG-IP ASM module is not used to support content filtering as part of the traffic management functions of the BIG-IP Core, this is not applicable. When content filtering is performed as part of the traffic management functionality, verify the BIG-IP ASM module is configured to update malicious code protection mechanisms and signature definitions whenever new releases are available in accordance with organizational configuration management policies and procedures. Verify the BIG-IP ASM module is configured to update malicious code protection mechanisms and signature definitions when providing content filtering to virtual servers for whenever new releases are available in accordance with organizational configuration management policies and procedures. Navigate to the BIG-IP System manager >> Security >> Options >> Application Security >> Attack Signatures >> Attack Signature Updates. Review the following settings to confirm compliance with organizational configuration management policies and procedures: Update Mode is set to "Manual", unless defined differently by the Organization. Delivery Mode is set to "Automatic", unless defined differently by the Organization. Verify that "Auto Apply New Signatures Configurations After Update" is NOT "Enabled", unless defined differently by the Organization. If the BIG-IP ASM module does not update malicious code protection mechanisms and signature definitions whenever new releases are available in accordance with organizational configuration management policies and procedures, this is a finding.

Check Text ( C-15713r290532_chk )

If the BIG-IP ASM module is not used to support content filtering as part of the traffic management functions of the BIG-IP Core, this is not applicable.

When content filtering is performed as part of the traffic management functionality, verify the BIG-IP ASM module is configured to update malicious code protection mechanisms and signature definitions whenever new releases are available in accordance with organizational configuration management policies and procedures.

Verify the BIG-IP ASM module is configured to update malicious code protection mechanisms and signature definitions when providing content filtering to virtual servers for whenever new releases are available in accordance with organizational configuration management policies and procedures.

Navigate to the BIG-IP System manager >> Security >> Options >> Application Security >> Attack Signatures >> Attack Signature Updates.

Review the following settings to confirm compliance with organizational configuration management policies and procedures:

Update Mode is set to "Manual", unless defined differently by the Organization.

Delivery Mode is set to "Automatic", unless defined differently by the Organization.

Verify that "Auto Apply New Signatures Configurations After Update" is NOT "Enabled", unless defined differently by the Organization.

If the BIG-IP ASM module does not update malicious code protection mechanisms and signature definitions whenever new releases are available in accordance with organizational configuration management policies and procedures, this is a finding.

Fix Text (F-15711r290533_fix)
If the BIG-IP Core performs content filtering as part of the traffic management functionality, configure the BIG-IP ASM module to update malicious code protection mechanisms and signature definitions whenever new releases are available in accordance with organizational configuration management policies and procedures.